Skip to content

fix: unify Docs dropdown nav and normalize docs index styling#236

Merged
GsCommand merged 1 commit into
mainfrom
codex/fix-docs-dropdown-navigation-consistency
May 21, 2026
Merged

fix: unify Docs dropdown nav and normalize docs index styling#236
GsCommand merged 1 commit into
mainfrom
codex/fix-docs-dropdown-navigation-consistency

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • Rebuilt pages had inconsistent top navigation where some pages used an old Docs link while others used the new dropdown pattern, causing UX and accessibility regressions.
  • The docs index (/docs.html) retained legacy dark/monospace styling in places and needed to match the light ENS/Stripe visual direction used by rebuilt pages.
  • Use the /docs/wrap-your-agent.html Docs dropdown as the canonical, clickable pattern so every rebuilt public page has a single predictable nav behavior.

Description

  • Standardized the top navigation markup and dropdown behavior to the canonical pattern (<li class="nav-drop"><a href="/docs.html">Docs ▾</a>…</li>) across rebuilt public pages and injected the matching .nav-drop CSS where needed, while preserving hover/focus access and mobile behavior.
  • Made the Docs label clickable to /docs.html (instead of a non-clickable button) and preserved the full dropdown menu items: Docs Home, Wrap Your Agent, Production Proof, Runtime, MCP Bridge, Schemas, API Reference, Trust Verification, and Claim / Namespace Activation.
  • Updated public/docs.html styling and header/nav to align with the light rebuilt pages and current logo treatment, while keeping Docs Home as the index page content unchanged beyond nav/footer adjustments.
  • Files updated: public/index.html, public/protocol.html, public/capabilities.html, public/verify.html, public/sdk-records.html, public/docs.html, public/stack-proof-demo.html, public/claim.html, public/runtime.html, and public/trust-verification.html; no API routes, schemas, or page body content (other than nav/footer consistency) were changed and no files were deleted.

Testing

  • Ran npm install which completed successfully with no errors.
  • Ran npm test and all automated tests passed (26 tests run, 26 passed, 0 failed).
  • Attempted npm run build but no build script exists in package.json, so no build was executed in this repo.

Codex Task

@vercel
Copy link
Copy Markdown

vercel Bot commented May 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
commandlayer-commandlayer-org Ready Ready Preview, Comment May 21, 2026 12:53am
commandlayer-org Ready Ready Preview, Comment May 21, 2026 12:53am
commandlayer-org111 Ready Ready Preview, Comment May 21, 2026 12:53am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant